And with CMS technology evolving to cover completely new deployment topologies such as cloud scalability, it is quite possible that the software editor will need to modify the architecture to introduce such capabilities. So a migration path will be needed, and it will, in a lot of cases, include some manual work (yes, despite the marketing that says that it is 100% seamless and effortless :))
The response to the concerns is always met with a short and simple question: “Haven’t’ you heard of migration paths?” Why of course!
There doesn't seem to be an automated migration path to convert Webtop/Taskspace based applications to D2/xCP 2.0 and customers might have to spend hefty sum to redevelop the same on newer platforms, which will be a painful exercise and might drive customers towards alternate solutions
What collaboration technology is used within your organisation? It's highly unlikely that you will be able to answer this question with just one word. "Collaboration" means so many different things to different people, and as a result most of us use several - or even many -...
2 Comments - Another side to this is the exit/migration path of course; recognising from the outset that this tool that we are standardising on is our best choice right now, but at some point in the future this will more than likely need to change, and therefore what will we need to be able to do at that point?